Headset device and a device profile management system and method thereof

ABSTRACT

Most computer operating systems are able to automatically configure the coupled computer peripheral audio device for use with the computer operating system without the need for installation of a specific driver. However, when these computer peripheral audio devices are detected by the computing system, a generic audio device control configuration is often assigned to them and whatever customized settings previously configured by the user will be lost and replaced with a new set of unfamiliar setting. This poses much inconvenience and hassle to gamers when they use a different computing system or machine. Described according to an embodiment of the invention is a headset device and a device profile management method, operating on a computing cloud, comprising steps for receiving client data provided by a computing system detecting coupling of an audio device thereto and for retrieving configuration data corresponding to the client data for use in configuring the audio device by the computing system.

FIELD OF INVENTION

The present invention relates generally to a headset device based onvirtualised surround sound technologies based on Head Related TransferFunctions (HRTF). In particular, the invention relates to a HRTF-basedheadset device and the system and method for managing the device forcomputing systems.

BACKGROUND

Many players in the audio industry that have used principles of HRTF inaudio devices to recreate virtual surround sound. Some devicemanufacturers rely solely on the principles of HRTF, and utilise filterson sounds to alter the phase and gain of those sounds which providepositional cues. This is a very rudimentary method and does not work onmost users effectively as certain sounds only appear louder or softer ormerely seem to echo in each ear, instead of accurate reproduction ofsounds to mimic the spatialisation effects as experienced in real-life.Listening to sounds via bone conduction, for example, throughcommercially available “bonephones”, may seem to produce sounds withstereo effects, but true 3D-spatialisation effects have yet to beachieved in current technologies.

Others use FFT (Fast Fourier transform) convolution to process a numberof variables, such as the phase, gain, as well as refractions of soundsoff the user's head, pinnae and body. This is a more accurate method,but many such technologies provide sound filters that are short and canonly provide a limited number of positional cues before the digitalsignal processing (DSP) begins processing other new sounds.

Both these methods will give sounds with positional cues that the user'sbrain can use to determine the position of a sound, but are associatedwith DSPs that can only process algorithms and variables at 34 MIPS(Millions of Instructions per Second).

In addition, due to variations in the shape, size and pinnae of the earsacross individuals of a population, how a sound is perceived is alsodifferent across individuals. Thus, while select individuals consistingof approximately 20% of the population may be able to experience thevirtual surround sound through current offerings of HRTF devices, thesound reproduction remains unconvincing for the remaining others. Thelow rate of true reproduction of virtual surround sound in currentofferings of HRTF devices is also due to the fact that positional cuesof recorded sounds are based on a single reference recording of amannequin's head. In the case for most gamers, the virtual surroundsound that is reproduced in current generation HRTF technologies are notsuited for high-precision gaming where accurate surround soundenvironments are contributing factors towards a gamer's overall speed,precision and control in a game. Hence, there is an unmet need forheadset devices which can provide true-to-life positional audio/virtualsurround sound and which can be customised for consistent optimum audioperformance for all gamers.

Further, as speed and accuracy are of significant importance to gamersan individual gamer's familiarity and consistency in the audio settingsand/or audio device configurations may determine how one performs in thegame. Typically, frequent gamers have a specific set of customiseddevice configurations uniquely suited for their game play. For example,an individualised combination of keys specific to a gamer's preferenceor optimized for a gamer's performance on a user interface (UI) devicesuch as a keyboard can be programmed to initiate an event duringgameplay. In the case of audio/headset devices, should a calibrationsystem exist, such calibration settings can also be programmed andsaved. Further, owing to the unique physical qualities of eachindividual's ears, there can be calibration of audio settings and/orheadset device settings to optimise virtual surround sound performancefor the individual. Gamers often do not break away from this set ofconfigurations as it allows them familiarity and consistency, and hencespeed and control during gaming.

It is not uncommon for gamers to be equipped with their own set ofpreferred peripheral devices. Computer peripheral devices include butare not limited to headset/audio devices, computer mice, keyboards,handheld gaming consoles and joysticks. Known computer peripheraldevices are typically interchangeable and can be used with differentcomputer systems and platforms. Most computer operating systems are ableto automatically configure the coupled computer peripheral device foruse with the computer operating system without the need for installationof a specific driver. However, when these peripheral devices aredetected by the computing system, a generic device control configurationis often assigned to them and whatever customised settings previouslyconfigured by the user will be lost and replaced with default settings.This poses much inconvenience and hassle to gamers when they enterLAN-gaming shops or utilise computers for their gaming pleasures as theywould have to reconfigure the control settings to suit theirpreferences.

There is, therefore, an apparent need for a method whereby these devicesettings and configurations can be stored and retrieved on the fly sothat users can do away with the hassle of re-configuring their controlsettings, including audio settings, whenever they use a differentplatform to access the different peripheral devices, including differentaudio devices.

SUMMARY

In accordance with a first aspect of the invention, there is disclosed aprofile management method comprising receiving client data provided by acomputing system and the client data comprising device data isdescriptive of an audio device in signal communication with thecomputing system. The device data is further descriptive of the userinteractions identifiable by the audio device and one of a plurality ofdevice profiles is associated with the device data and each of theplurality of device profiles having configuration data associatedtherewith; In a further step, the computing system is provided theconfiguration data associated with the one of the plurality of deviceprofiles to the computing system for configuring operation of the audiodevice with the computing system, in response to at least a portion ofthe user interactions identifiable by the audio device.

In accordance with a second aspect of the invention, there is discloseda profile management system comprising a controller module for receivingclient data provided by a computing system, and the client datacomprises device data being descriptive of an audio device in signalcommunication with the computing system. The device data is furtherdescriptive of the user interactions identifiable by the audio device.The profile management system also comprises a storage module havingstored thereon a plurality of device profiles, each of the plurality ofdevice profiles having device configuration data associated therewith.The profile management system further comprises a processor module forassociating one of a plurality of device profiles stored on the storagemodule with the device data, and the configuration data associated withthe one of the plurality of device profiles is providable by thecontroller module to the computing system for configuring operation ofthe audio device with the computing system in response to at least aportion of the user interactions identifiable by the audio device.

In accordance with a third aspect of the invention, there is disclosed anon-transitory machine readable medium having stored therein a pluralityof programming instructions, which when executed, the instructions causethe machine to receive client data provided by a computing system. Theclient data comprising device data is descriptive of an audio device insignal communication with the computing system and the device data isfurther descriptive of the user interactions identifiable by the audiodevice. The plurality of programming instructions when executed, alsocauses the machine to associate one of a plurality of device profileswith the device data and each of the plurality of device profiles havingconfiguration data associated therewith. The plurality of programminginstructions when executed, further causes the machine to provide theconfiguration data associated with the one of the plurality 15 of deviceprofiles to the computing system for configuring operation of the audiodevice with the computing system in response to at least a portion ofthe user interactions identifiable by the audio device.

In accordance with a fourth aspect of the invention, there is disclosedan audio device comprising a storage module for storing a controlfunction, the control function being associated with head-relatedstructure of a user. The audio device also comprises a processor forreceiving audio signals being descriptive of audio sounds and spatialpositions corresponding with the audio sounds, the processor forprocessing the received audio signals into control signals based on thecontrol function. The audio device further comprises a transducer fortransducing control signals into the audio sounds for delivery to theuser when the audio device is in use thereby and the spatial positionsof the audio sounds are processed by the processor to substantiallyconform to the head-related structure of the user based on the controlfunction.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a system diagram of a HRTF-based headset device;

FIG. 2 shows a system diagram of a profile management system residing ona computing cloud according to an exemplary embodiment of the invention;

FIG. 3 shows a system diagram of the profile management system of FIG. 2with user-interfaces in signal communication with computing systemscoupled thereto;

FIG. 4 shows a process flow diagram of a profile management method forimplementation by the profile management system of FIG. 2;

FIG. 5 shows a process flow diagram of a device discovery method forimplementation by the computing systems of FIG. 3; and

FIG. 6 shows an arrangement of device profile, configuration data, useridentifier and authentication data residing on the profile managementsystem of FIG. 2.

DETAILED DESCRIPTION

Reference will now be made in detail to an exemplary embodiment of thepresent invention, examples of which are illustrated in the accompanyingdrawings. While the invention will be described in conjunction with theembodiment, it will be understood that they are not intended to limitthe invention to these embodiments. On the contrary, the invention isintended to cover alternatives, modifications and equivalents, which maybe included within the spirit and scope of the invention as defined bythe appended claims. Furthermore, in the following detailed descriptionof embodiments of the present invention, numerous specific details areset forth in order to provide a thorough understanding of the presentinvention. However, it will be recognized by one of ordinary skill inthe art that the present invention may be practiced without thesespecific details. In other instances, well-known methods, procedures,components, and circuits have not been described in detail as not tounnecessarily obscure aspects of the embodiments of the presentinvention

For purposes of brevity and clarity, descriptions of embodiments of thepresent invention are limited hereinafter to the transfer and managementof device profiles, in particular, device configurations, for a clientdevice associated with a computing system. This however does notpreclude embodiments of the invention where fundamental principalsprevalent among the various embodiments of the invention such asoperational, functional or performance characteristics are required.

An exemplary embodiment of the invention, a profile management method100, is described hereinafter. The profile management method 100 ispreferably for managing configuration of audio devices 18 including, butnot limited to, headset device coupled to a computing system 20 incommunication with a computing cloud 22.

The computing system may comprise, but is not limited to, a personalComputer (PC), a network server, a laptop, a computer tablet, a gamingconsole, or a smartphone. An audio device 18, may comprise, but is notlimited to, a headset device featuring HRTF technology or a pair ofearphones. A headset device featuring HRTF technology typically allowsfor audio playback of the source material that has been set to output5.1 or 7.1 (channels) audio through multi-sound channels within theheadset device.

An exemplary embodiment of the HRTF-based headset device 50, withreference to FIG. 1, comprises a memory storage module 52, a processor54, a transducer 56 and an audio input interface 58. The storage module52 may comprise, but are not limited to, a built-in flash memory or aremovable memory disk, for the storage of saved user settings of theHRTF-based headset device 50. The processor 54 executes a plurality ofprogramming instructions which may be stored within the storage module52 to result in the communication of signals between the HRTF-basedheadset, a computing system and a computing cloud which the HRTF-basedheadset may be coupled to, during the running of various functions asprogrammed in the programming instructions. The transducer 56 comprisesbut are not limited to, a pair of ear cups or a pair of ear phones. Theaudio input interface 58 comprises a device which allow for the input ofaudio sequences for sound recordings or voice recordings, such as amicrophone.

The configuration of a HRTF-based headset device 50 settings comprisescalibration of user settings in relation to at least one of the shape,size and pinnae of the user's ears. The configuration of a HRTF-basedheadset device 50 settings may also comprise the use of a device, suchas but are not limited to, a microphone forming part of the HRTF-basedheadset device 50, to obtain configurations of the users' ears,including but not are limited to, the shape, size and pinnae of theears. For example, the length of a microphone may include measurementguides to obtain at least an approximation of various physical aspectsof a user's ears.

Additionally, the user settings of a HRTF-based headset device 50 may beconfigured according to at least one of a plurality of virtualized earpinnae configurations from a database, the plurality of virtualized earpinnae configurations being indicative of at least a majority of thehuman population. The database of a plurality of virtualized ear pinnaeconfigurations may be located on at least one of a storage module 52within the HRTF-based headset device 50, a storage module 52 within acomputing system coupled to the HRTF-based headset device 50 and on acomputing cloud coupled to the HRTF-based headset device 50. Theprocessor 54 of the HRTF-based headset device 50 may further process thesource material of the audio output based on the saved user settings ofthe HRTF-based headset.

Further described, with reference to FIGS. 2 to 6, is a device profilemanagement system 24, residing on the computing cloud 22, for applyingthe profile management method 100.

Generally, the profile management system 24 enables a configuration foraudio devices 18 to be created by a user so that the configuration canbe readily accessed from different locations or from different computerterminals when the same or similar type of audio device 18 is used. Forexample, when a user brings a HRTF-based headset device 50 from locationto location, the user does not have to reconfigure the HRTF-basedheadset device 50 at each new location or at a new computer terminal.The configuration for the audio device 18, including the preferredsettings therefor, are downloadable via the computer terminal the audiodevice 18 is coupled to. This even applies to newly acquired deviceswhere the audio device 18 thereof can be configured for use “out of thebox” via downloading the corresponding configuration previously createdby a user, a third party, the device manufacturer or an applicationdeveloper, for example, a gaming application. The configurations for theaudio devices 18 are preferably stored on one or more servers with eachconfiguration catering to a specific, or similar, audio device type andrelating to a specific user identified by a user identifier. Download ofthe configuration can be initiated via various means including by thecoupling of the audio device 18 to a computer system, connecting to aspecific network address, for example an IP address or a URL, launchingof a particular application or game application or through operating ofcontrols within an application. Preferably, information on the audiodevice type is providable to the one or more server so that theconfiguration corresponding to the audio device type, and preferablyfurther corresponding to a particular user ID, can be identified fordownload and subsequent configuration of the corresponding audio device18.

With reference to FIGS. 2 to 6, the computing cloud 22 comprises one ormultiple server systems 26 inter-networked and configured to function asthe profile management system 24. Communication pathway between thecomputing cloud 22 and the computing system 20 is preferably providedvia a local area network (LAN), a wide area network (WAN), the Internet,cellular networks, data networks, dedicated networks or a combination ofany thereof.

The profile management system 24 comprises a controller module 28 forreceiving client data 29 provided by the computing system 20, a storagemodule 30 for storing a plurality of device profiles 31 and a processormodule 32. The client data 29 comprises device data 34 for associatingwith one of the plurality of the device profiles 31 by the processormodule 32.

The profile management method 100 comprises a step 102 of receiving theclient data 29 providable by the computing system 20 by the profilemanagement system 24, a step 104 of associating one of the plurality ofdevice profiles 31 within the profile management system 24 with theclient data 29 and a step 106 of providing configuration data 36associated with one of the plurality of device profiles 31 to thecomputing system 20 for configuration of the audio device 18 thereafter.

The device data 34 is preferably descriptive of the audio device 18associated with the computing system 20. The device data 34 is furtherdescriptive of the user interactions identifiable by the audio device18. Preferably, the audio device 18 is one of a computer peripheralaudio device coupled with an interface formed integral with thecomputing system. Examples of computer peripheral audio devices includebut are not limited to, a HRTF-based headset device or earphones.Alternatively, the audio device 18 includes devices which are couplablewith a computing system for use with or forms part of the computingsystem 20. For example, a HRTF-based headset device 50 may comprise ajack plug (the male connector for transmitting audio signals) of aHRTF-based headset which is connectable to a jack socket (the femaleconnector for transmitting audio signals) of a computing system. AHRTF-based headset may also be couplable with a computing system via awireless connection such as, but are not limited to, a infra-red-basedconnection, a Bluetooth connection, or a wireless internet connection.Detection and recognition of the audio device 18, or its functionalequivalent, occurs when the audio device 18 is in signal communicationwith the computing system 20. The computing system 20 generates thedevice data 34 for the audio device 18 when the audio device 18 isrecognised thereby. For example, if the audio device 18 is a HRTF-basedheadset device 50, the user interactions identifiable by at least one ofthe HRTF-based headset device 50 and the computing system comprise, butare not limited to, the connection of the HRTF-based headset device 50'sjack plug to the computing system's jack socket; wireless coupling ofthe HRTF-based headset device 50 with the computing system; detection ofsound input through the audio input interface 58 such as a microphone;volume adjustment via volume controls coupled to the HRTF-based headsetdevice 50; sound channel adjustment and selection via sound channeladjustment/selection controls coupled to the HRTF-based headset device50; volume adjustment of each sound channel via sound channel volumecontrols attached to the HRTF-based headset device 50; selection of atleast one of a plurality of virtualized ear pinnae configurations from adatabase for calibration of the HRTF-based headset device 50; andinputting of user settings through an interface for calibration of theHRTF-based headset device 50.

When a user couples the audio device 18 to the computing system 20 innetwork communication with the computing cloud 22, the profilemanagement system 24 is able to receive the client data 29 generated bythe computing system 20. The audio device 18 may be connected to thecomputing system 20 via wired or wireless signal connection. Detectionof the audio device 18 can be configured by the user to be in responseto coupling of the audio device 18 to the computing system 20 or to beeffected by the user by executing a routine or application on thecomputing system. Application programming interfaces (APIs) orcomponents of software development kits (SDKs) is preferably madeavailable for programmers, game developers and application developers toincorporate the function of detecting the audio device 18 onto theircomputing systems 20 and software applications. This will provide theuser with better control over how and when the audio device 18 is to bedetected for discovery and sending of the client data 29 to the profilemanagement system 24. The APIs and components of SDKs may be providedfor development of auto-executable routines residing on the audio device18 for initiating the profile management method 100 upon detectionthereof by the computing system 20 when the audio device 18 is coupledthereto. In such an instance, the device data 34 specific to the audiodevice 18 may be pre-defined and preloaded onto the audio device 18,preferably, onto a memory module residing on the audio device 18. Forexample, the device data comprising, but are not limited to, saved usersettings or a pre-selected at least one of a plurality of virtualizedear pinnae configurations from a database for a HRTF-based headsetdevice 50 may be downloaded onto the HRTF-based headset device 50'sstorage module 52 from the computing cloud, or uploaded from the storagemodule 52 of the HRTF-based headset device 50 onto the computing cloud.

Preferably, the client data 29 further comprises identifier data 38uniquely matched to at least one of a plurality of user identifiers 40residing on the storage module 30. Upon receiving of the client data 29by the profile management system 24 in the step 102, the profilemanagement system 24 further processes the client data 29 for eitheruser registration or log-on to the profile management system 24. For anexisting user with an identity existing as one of the plurality of useridentifiers 40 on the storage module 30, access to the profilemanagement system 24 triggers the processor module 32 to associate theparticular one of the user identifiers 40 with the identifier data 38.Upon associating the one of the user identifiers 40 with the identifierdata 38, the one of the device profiles 31 and the configuration data 36corresponding thereto are consequently identified. As an alternativeover the identifier data 38 or in the absence of the identifier data 38,the device data 34 may be used for identifying the corresponding one ofthe device profiles 31 and the corresponding configuration data 36. Inan event where none of the device profiles 31 exactly matches the devicedata 38, a closest matching one of the device profiles 31 may beselected instead. The controller module 28 can be configured to select aclosest matching one of all the device profiles 31 on the storage module30 or a closest matching one of only the device profiles 31 associatedwith a particular one of the user identifiers 40.

In an example of use of the profile management system 24, a user coupleshis HRTF-based headset device 50, the audio device 18, to a publiccomputer, the computing system 20. One or both of the HRTF-based headsetdevice 50 and the public computer may be pre-loaded with a sub-routineto automatically connect to the profile management system 24 forinitiating the profile management method 100. Alternatively, the usercan Manually connect with the profile management system 24, for example,via a URL using a web browser. Once the profile management method 100has been initiated, the HRTF-based headset device 50 will sendinformation, the client data 19, to the profile management system 24indicating that it is of a HRTF-based headset device 50 type, the devicedata 34. The sent information can include the user's name or a useridentifier, the identifier data 38. On the profile management system 24,the user identifier 40 matching with the user's name may have multipledevice profiles 31 associated therewith, for example various types ofdevices including, but are not limited to, a HRTF-based headset device50, 3-D mouse, a specific model of gaming mouse and a multi-touchdevice. With the sent information indicating that the HRTF-based headsetdevice 50 is of a HRTF-based headset device 50 type, the profilemanagement system 24 can isolate the corresponding one of the multipledevice profiles 31 for extracting the configuration data 36corresponding 36 thereto. The configuration data 36 can include, for theHRTF-based headset device 50, a library of, but not limited to, audiosettings and corresponding instructions for download to the publiccomputer for configuring use of the HRTF-based headset device 50 withthe public computer. Upon the HRTF-based headset device 50 beingconfigured with the public computer, the user can immediately interactwith the HRTF-based headset device 50 to generate instructions withaudio settings the user is familiar with without having to recalibrateor reconfigure audio settings and corresponding instructions.

In another example of use of the profile management system 24, theHRTF-based headset device 50 is a newly acquired device connectable tothe profile management system 24, via the user's personal computer, thecomputing system 20, for locating and downloading a popular audiosettings library, a personal audio settings library or a library ofaudio settings provided by the manufacturers of the HRTF-based headsetdevice 50, the configuration data 36 for use in configuring theHRTF-based headset device 50 with the user's personal computer. In yetanother example of use of the profile management system 24, the audiodevice 18 is a HRTF-based headset device 50 for use with a publiccomputer, the computing system 20. A user with his preferred settings,the configuration data 36, stored on the profile management system 24 isable to connect the public computer to the profile management system 24for downloading the configuration data 36 to the public computer. Theconfiguration data for the gaming mouse could include a popular audiosettings library, a personal audio settings library or a library ofaudio settings provided by the manufacturers. The availability of theconfiguration data 36 on the profile management system 24 allows theuser to quickly configure the HRTF-based headset device 50, or otheraudio devices 18, when using the public computer.

For retrieval of configuration data 36 from the profile managementsystem 24 in the step 104, the user may either log-on to the profilemanagement system 24 to retrieve stored configuration data 36 accessibleto the public or choose to retrieve device data previously uploaded tothe profile management system 24 associated with the user identifier 40belonging to the user. Download of the configuration data 36 by otherusers is preferably determined by permission settings associated withthe configuration data 36. Upon receiving client data 29 by thecontroller module 28, the profile management system 24 may initiateautomated download of the configuration data 36 associated with thedevice profile 31 matching with the device data 34 of the providedclient data 29 in the step 106.

Preferably, the step 102 of receiving client data 29 comprises a step108 of receiving authentication information (unreferenced) from thecomputing system 20, for example a password provided by a user, toauthenticate the identifier data 34 using the authentication data 42corresponding thereto. Preferably, the profile management system 24 isconfigured such that the configuration data 36 in association with theidentified one of the device profiles 31 will only be provided by thecontroller module 28 to the computing system 20 in the step 106 when theidentifier data 34 is authenticated. Preferably, the configuration data36 substantially defines interactions between the audio device 18 and atleast one of an application and an operating platform operating on thecomputing system 20. In both gaming and non-gaming applications, theconfiguration data 36 of a HRTF-based headset device 50 can be the usersettings comprising, but are not limited to, calibrations according tothe user ears' physical specifications or the pre-selection of at leastone of a plurality of virtualized ear pinnae configurations, audiooutput volume settings, audio input volume settings such as themicrophone volume settings of a microphone of the HRTF-based headsetdevice 50, sound channel adjustment settings, sound channel volumesettings and voice-activated commands through a microphone of theHRTF-based headset device 50.

When there exists a mismatch of operating platforms supported by thecomputing system 20 and which the stored configuration data operates on,the step 106 comprises a step 112 of processing the configuration data36 for compliance with an operating platform so that the configurationdata 36 downloadable from the profile management system 24 can becorrectly recognised and configured for operation of the audio device 18with the computing system 20.

The operating platform is definable by platform data (unreferenced)constituting a portion of the client data 29 generatable by thecomputing system 20 for provision to the profile management system 24.

Complementary to and in association with the profile management method100, there exists a device discovery method 116 configurable by the userfor editing of data on the profile management system 24. The devicediscovery method 116 is preferably applied by the computing system 20.The device discovery method 116 comprises a step 124 of providing clientdata 29 for log-on to the profile management system 24 and a step 126 ofuploading the device data 34 to the profile management system 24.

The step 124 further comprises at least one of a step 132 for detectingcoupling of the audio device 18 to the computing system 20, a step 134for manually keying in of identifier data 38 to effect log-on to theprofile management system 24 and a step 136 for registering a new useridentifier 40 with the profile management system 24. Preferably in thestep 132, the computing system 20 detects signal communication of theaudio device 18 with and generates the client data to effect anautomated log-on to the profile management system 24 by associating theidentifier data 38 with one of the device profiles 31. Alternatively,the user may configure settings of the device discovery method 116 suchthat a log-on prompt will be initiated for requesting provision of theidentifier data 38 upon the computing system 20 detecting signalcommunication of the audio device 18 therewith. The user will then berequired to manually key-in the identifier data 38 in the step 134 foraccess to the profile management system 24. In the step 136, a new usermay register with the profile management system 24 by following throughwith a registration process. The registration process may request thenew user to either manually key in new identifier data 38 to be storedon the storage module 30 as one of the user identifiers 40 or couple anew device to the computing system 20 for extraction of the identifierdata 38 therefrom.

In the step 126, a user may define and upload new client data 24 ontothe storage module 30 in the profile management system 24 under one ofthe user identifiers 40. The device data 34 in association with theclient data 29 will be stored in the profile management system 24 as oneof the device profiles 31. The configuration data 36 for new audiodevice settings and configuration will also be uploaded for storage bythe profile management system 24 and will be registered as beingassociated with the newly created one of the device profiles 31.Preferably, the profile management system 24 allows for subsequentediting of the configuration data 36 after being uploaded to the storagemodule 30.

In the gaming context, for gamers who are always on the move, theirpreferred settings configurations for computer peripherals, eithergeneral settings or game-specific settings, are made storable andaccessible through a multitude of devices and platforms. In LAN-gamingshops or at any public access terminal, gamers have their preferredsettings configurations on the fly and downloadable via the profilemanagement system 24 to any terminal or platform in networkcommunication thereto. Users with new gaming devices can also utilisethe profile management system 24 to obtain a set of basic settingconfiguration for the audio device 18 without having to manuallyconfigure control for any possible manipulation of the audio device 18.Update or modification of setting configurations from any computingsystem 20 in network communication with the profile management system 24is also an available option.

Additionally, the profile management system 24 is able to process usageinformation and data stored in the storage module 30 for a variety ofapplications, including data analytics, and for access by users or thirdparties. The storage module 30 is preferably accessible by a thirdparty. The third party includes, for example, a games developer, anadvertiser or a network service provider. In addition, knowledge of theconfiguration preferences of users, in particular gamers, will enablegame developers to design products that will better satisfy consumers.

In a non-gaming context, for example, when a user connects a HRTF-basedheadset device 50 to a profile management system 24 on the computingcloud 22, or when voice command memos are being downloaded from theHRTF-based headset device 50 to the computing system 20, configurationspreviously stored in the HRTF-based headset device 50 for manipulationof the audio device 18 as well as specific voice activated commands usedpreviously in the HRTF-based headset device 50 can be downloaded fromthe profile management system 24 and thereby be used with the computingsystem 20, having the various settings, commands and controls mimickedseamlessly.

The profile management method 100 preferably resides on the profilemanagement system 24 as a plurality of instructions stored on anon-transitory machine readable medium of the profile management system24. It is preferred that the instructions, when executed, cause theprofile management system 24 to perform the step of the profilemanagement method 100. Similarly, the device discovery method 116 existson the computing system 20 as a plurality of instructions stored on anon-transitory machine readable medium thereof. It is preferred that theinstructions, when executed, cause the profile management system 24 toperform at least one of the steps of the device discovery method 116.

In a forgoing manner, a profile management method 100 and profilemanagement system 24 are described according to exemplary embodiments ofthe invention. Although only a number of embodiments of the inventionare disclosed in this document, it will be apparent to one skilled inthe art in view of this disclosure that numerous changes and/ormodifications can be made to the disclosed embodiments without departingfrom the scope and spirit of the invention.

What is claimed is:
 1. A profile management method comprising: receivingclient data provided by a computing system, the client data comprisingan identifier data, a device data and a platform data, wherein theidentifier data is indicative of a user of an audio device incommunication with the computing system, wherein the device data isdescriptive of a type of the audio device and wherein the platform datais descriptive of an operating platform of the computing system;matching a user identifier of a plurality of user identifiers with theidentifier data, wherein each user identifier of the plurality of useridentifiers is associated with a set of device profiles; identifying onedevice profile of the set of device profiles associated with the useridentifier matched with the identifier data, that corresponds to thedevice data, wherein each device profile of the set of device profileshas a configuration data associated therewith; processing theconfiguration data based on the platform data to enable theconfiguration data that is processed to be operable with the computingsystem; detecting coupling of the audio device to the computing system;downloading the configuration data that is associated with theidentified one device profile and that is processed, from a server tothe computing system, upon the detection of the coupling; andconfiguring the audio device for operation with the computing system inresponse to the ear pinnae configuration associated with the user of theaudio device; wherein the audio device is a computer peripheral audiodevice; wherein the configuration data caters to the type of the audiodevice.
 2. The profile management method as in claim 1, wherein the typeof the audio device is one of a HRTF-based headset, non-HRTF-basedheadset or non-HRTF-based earphones.
 3. The profile management method asin claim 1, further comprising: receiving authentication data from thecomputing system; and authenticating the identifier data using theauthentication data, wherein the configuration data is provided to thecomputing system in response to the identifier data being authenticated.4. The profile management method as in claim 1, wherein theconfiguration data defining interactions between the audio device and atleast one of an application and the operating platform operating on thecomputing system.
 5. The profile management method of claim 1, whereinthe device data is further descriptive of user interactions identifiableby the audio device; wherein configuring operation of the audio devicewith the computing system is in response to at least a portion of theuser interactions identifiable by the audio device.
 6. The profilemanagement method of claim 1, further comprising: obtaining an earpinnae configuration of the user of the audio device, using the audiodevice.
 7. A profile management system comprising: a controller moduleconfigured to receive client data provided by a computing system, theclient data comprising an identifier data, a device data and a platformdata, wherein the identifier data is indicative of a user of an audiodevice in communication with the computing system, wherein the devicedata is descriptive of a type of the audio device and wherein theplatform data is descriptive of an operating platform of the computingsystem; a processor module configured to match a user identifier of aplurality of user identifiers with the identifier data, wherein eachuser identifier of the plurality of user identifiers is associated witha set of device profiles, and further configured to identify one deviceprofile of the set of device profiles associated with the useridentifier matched with the identifier data, that corresponds to thedevice data; a memory having stored thereon the set of device profiles,each device profile of the set of device profiles having a configurationdata associated therewith; wherein the processor module is furtherconfigured to process the configuration data based on the platform datato enable the configuration data that is processed to be operable withthe computing system; wherein the configuration data that is associatedwith the identified one device profile and that is processed isdownloadable by the controller module, from a server to the computingsystem, upon detection of coupling of the audio device to the computingsystem; wherein the processor module is further configured to configurethe audio device for operation with the computing system in response tothe ear pinnae configuration associated with the user of the audiodevice; wherein the audio device is a computer peripheral audio device;wherein the configuration data caters to the type of the audio device.8. The profile management system of claim 7, wherein the type of theaudio device is one of a HRTF-based headset, non-HRTF-based headset ornon-HRTF-based earphones.
 9. The profile management system of claim 7,wherein the device data being further descriptive of user interactionsidentifiable by the audio device; wherein user interactions identifiableby the HRTF-based headset device comprise: at least one of theconnection of the HRTF-based headset device's jack plug to the computingsystem's jack socket; wireless coupling of the HRTF-based headset devicewith the computing system; detection of sound input through an audioinput interface of the HRTF-based headset device; volume adjustment viavolume controls coupled to the HRTF-based headset device; sound channeladjustment and selection via sound channel adjustment/selection controlscoupled to the HRTF-based headset device; volume adjustment of eachsound channel via sound channel volume controls attached to theHRTF-based headset device; selection of at least one of a plurality ofvirtualized ear pinnae configurations from a database for calibration ofthe HRTF-based headset device; and inputting of user settings through aninterface for calibration of the HRTF-based headset device.
 10. Theprofile management system as in claim 7, further comprising: anauthentication module configured to receive authentication data from thecomputing system; and further configured to authenticate the identifierdata using the authentication data, wherein the configuration data isprovided to the computing system in response to the identifier databeing authenticated.
 11. The profile management system as in claim 7,the configuration data defining interactions between the audio deviceand at least one of an application and the operating platform operatingon the computing system.
 12. A non-transitory machine readable mediumhaving stored therein a plurality of programming instructions, whichwhen executed, the instructions cause the machine to: receive clientdata provided by a computing system, the client data comprising anidentifier data, a device data and a platform data, wherein theidentifier data is indicative of a user of an audio device incommunication with the computing system, wherein the device data isdescriptive of a type of the audio device and wherein the platform datais descriptive of an operating platform of the computing system; match auser identifier of a plurality of user identifiers with the identifierdata, wherein each user identifier of the plurality of user identifiersis associated with a set of device profiles; identify one device profileof the set of device profiles associated with the user identifiermatched with the identifier data, that corresponds to the device data,wherein each device profile of the set of device profiles has aconfiguration data associated therewith; processing the configurationdata based on the platform data to enable the configuration data that isprocessed to be operable with the computing system; detect coupling ofthe audio device to the computing system; download the configurationdata that is associated with the identified one device profile and thatis processed, from a server to the computing system, upon the detectionof the coupling; and configure the audio device for operation with thecomputing system in response to the ear pinnae configuration associatedwith the user of the audio device; wherein the audio device is acomputer peripheral audio device; wherein the configuration data catersto the type of the audio device.
 13. The non-transitory machine readablemedium as in claim 12, further comprising: receiving authentication datafrom the computing system; and authenticating the identifier data usingthe authentication data, wherein the configuration data is provided tothe computing system in response to the identifier data beingauthenticated.
 14. The non-transitory machine readable medium as inclaim 12, the configuration data defining interactions between the audiodevice and at least one of an application and the operating platformoperating on the computing system.